home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 2.2 KB | 60 lines | [TEXT/GEOL] |
- Item forwarded by A33 to A34
-
- Item 1890420 25-Nov-89 16:11
-
- From: SCHMUCKER1 Schmucker, Kurt
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: View signature "bug"
-
- The following view "glitch" caused me several days of befuddlement, so I
- thought I would pass it on.
-
- Upon issuing the menu command to bring up a dialog in my MacApp
- application, I fell into the debugger with the following lines:
-
- Unable to find subview: ' '
- ProgramBreak: Unable to find parent view for template
- stopped at Break TEVTHANDLER.DOCREATEVIEWS Seg#: 12 Self: $0065B1E0 is
- TQUADAPPLICATION
-
- (In case AppleLink ate the character in the quotes in the first line, it is the
- open square. The same character you see in the Chicago font for option-k or
- control-k.)
-
- I had constructed this dialog with ViewEdit, so that was the first thing I
- suspected. (Sorry Russ and Lonnie.) I looked around the view and everything
- seemed fine. There was no view with the open-square signature. I de-rezed the
- view and examined the textual version, and that, too, looked OK. I re-rezed
- the text and used the newly constructed view (again suspecting ViewEdit.) The
- problem was still there. I made sure that I had included the standard
-
- IF gDeadStripSuppression THEN
- BEGIN
- IF Member(TObject(NIL), TQWAboutBoxView) THEN;
-
- .
- .
- .
- END;
-
- technique to supress dead stripping of the view classes. In probing around
- with the debugger, I noticed that I had forgotten to provide a Fields method
- for the main view of the dialog. While adding it, I found the REAL problem.
-
- My main dialog view was descended from TDialogView (naturally), but I had
- made it with a TView template in ViewEdit, not a TDialogView one! ViewEdit had
- constructed it with proper view template records for a TView, but my MacApp
- code was expecting it to be a TDialogView subclass. Boom.
-
- Moral: Fancy tools like ViewEdit can really help you out, but they are
- still only as fool-proof as the person using them.
-
- If I can just chase done this one other bug - I'm SURE it is a compiler
- error ...
-
-
- Kurt
-
-